#css box generator

[elftwink]

am currently working on a neocities site (which i cannot give you the url for yet because im working on the css still and there's no content also it looks ugly still) and oh man does it take me back to ye olde days of custom theme editing on here. i still use a custom theme obvs but back in like 2014/2015ish when i was really into indie rp custom themes were all the rage and you would spend hours editing some character specific image for your bg and then another several hours trying to make the css line up with your image (never at any point did i attempt to actually like. learn html or css. i just read other people's theme codes and edited the parts i could understand and solved problems as they arose. i distinctly remember one time i was using a base that had two sidebars and i only wanted one and deleting the section broke the theme in disastrous ways [bc i had no idea what i was doing] so i literally just made all the elements in the sidebar transparent and moved them off the screen LMAO. the best i ever got was moving from fully built custom themes that i edited to base themes that i built off of)

anyway while im slightly better now (im even reading tutorials! am i following them? sorry i have to go i think someones calling me) i am using a layout builder to build the homepage so it is even more reminding me of mid-2010s tumblr. much like building off a base theme, and definitely easier to understand than tumblr theme building (this time i at least know what all the different pieces of code are doing, even when im not sure how or why, or how to duplicate the effect under slightly different circumstances. but progress is progress!).

a good but annoying thing about the layout that im using is that i havent actually edited the site wide stylesheet, just used internal css on that one page, so when i go to make literally any other page i'll have to start from scratch. this is good because i am learning a lot and i think without doing it this way i would end up with a bunch of useless stuff in the stylesheet that really should be page-specific that i would have to correct with internal or inline css later. annoying because what do you mean i have to make decisions about the sizing and positions of the content? i literally just did that

also im kind of nervous to touch the general stylesheet because im pretty sure what i'll actually want to do is have a couple of stylesheets for different 'sections' of the website, to maintain cohesion between pages of the 'same' type but still allow a lot of fun customization on a per-page basis, but that requires deciding what 'sections' i want on the website and that is a whole other can of worms. but also you can't start without starting so i should probably just try to build a really simple layout and go from there (after all, if it sucks, it's not like i can't just create a new stylesheet, or do the css for each page independently until i hit a groove that's actually worth moving to the stylesheet). but also first i have to finish this goddamn homepage. which means i gotta find a header image that doesn't look ugly as shit

[raincloud47]

Raspberry Delight

The css for the buttons is from a skin made by @ao3commentoftheday with the colors changed to make them more pink.

The pink icons were made by @zerafinacss

@zerafinacss also has pink stat icons that look really good with this skin. It would replace the language/words/chapters ect. with some cute pink icons.

If you want this skin, the code is under here!

First, you have to put these codes into the wizard.

After you save that, you just copy and paste this code:

#header .logo {

background-image: url("https://images.squidge.org/images/2024/03/30/AO3_imageset_pink.png");

background-size: 250px 1044px;

padding: 42px 0 0 60px;

width: 0 !important;

height: 0 !important;

background-position: -140px -749.6px;

}

#header ul.primary,

#header h2 {

box-shadow: none;

}

.required-tags .rating-notrated,

.required-tags .rating-general-audience,

.required-tags .rating-explicit,

.required-tags .rating-mature,

.required-tags .rating-teen,

.required-tags .category-femslash,

.required-tags .category-gen,

.required-tags .category-slash,

.required-tags .category-none,

.required-tags .category-het,

.required-tags .category-multi,

.required-tags .category-other,

.required-tags .complete-no,

.required-tags .complete-yes,

.required-tags .warning-yes,

.required-tags .warning-no,

.required-tags .warning-choosenotto,

.required-tags .external-work,

.status .private .text,

.status .public,

.status .hidden,

.status .rec,

.status .count,

.index .skins .icon,

.index .mystery .icon,

.index .tag .icon,

.index .tagset .icon,

.comment .icon .anonymous,

.comment .icon .visitor,

.abbreviated .icon .visitor,

.abbreviated .icon .anonymous,

.skins .primary .icon,

.admin .primary .icon,

.tagset .primary .icon,

.tag .primary .icon,

a.rss span,

p.kudos,

#symbols-key dl img,

#bookmark-symbols-key img,

img[src$="/images/skins/iconsets/default/icon_user.png"],

img[src$="/images/skins/iconsets/default/icon_collection.png"],

img[src$="/images/lockblue.png"] {

background-image: url("https://images.squidge.org/images/2024/03/30/AO3_imageset_pink.png");

background-size: 200px 835px;

}

#symbols-key dl img,

#bookmark-symbols-key img {

width: 0 !important;

height: 0 !important;

padding: 25px 0 0 25px;

}

img[src$="/images/skins/iconsets/default/rating-notrated.png"],

img[src$="/images/skins/iconsets/default/category-none.png"],

img[src$="/images/skins/iconsets/default/warning-no.png"] {

background-position: -150px 0px;

}

img[src$="/images/skins/iconsets/default/rating-general-audience.png"] {

background-position: -50px -25px;

}

img[src$="/images/skins/iconsets/default/rating-teen.png"] {

background-position: 0px -25px;

}

img[src$="/images/skins/iconsets/default/rating-mature.png"] {

background-position: -75px -25px;

}

img[src$="/images/skins/iconsets/default/rating-explicit.png"] {

background-position: -25px -25px;

}

img[src$="/images/skins/iconsets/default/category-femslash.png"] {

background-position: -25px 0px;

}

img[src$="/images/skins/iconsets/default/category-het.png"] {

background-position: -75px 0px;

}

img[src$="/images/skins/iconsets/default/category-gen.png"] {

background-position: -50px 0px;

}

img[src$="/images/skins/iconsets/default/category-multi.png"] {

background-position: -100px 0px;

}

img[src$="/images/skins/iconsets/default/category-other.png"] {

background-position: -125px 0px;

}

img[src$="/images/skins/iconsets/default/warning-choosenotto.png"] {

background-position: -125px -25px;

}

img[src$="/images/skins/iconsets/default/warning-yes.png"] {

background-position: -150px -25px;

}

img[src$="/images/skins/iconsets/default/warning-external-work.png"] {

background-position: -75px -50px;

}

img[src$="/images/skins/iconsets/default/complete-no.png"] {

background-position: -100px -25px;

}

img[src$="/images/skins/iconsets/default/complete-yes.png"] {

background-position: -175px -25px;

}

img[src$="/images/skins/iconsets/default/bookmark-rec.png"] {

background-position: -100px -50px;

}

img[src$="/images/skins/iconsets/default/bookmark-public.png"] {

background-position: -125px -50px;

}

img[src$="/images/skins/iconsets/default/bookmark-private.png"] {

background-position: -175px -50px;

}

img[src$="/images/skins/iconsets/default/bookmark-hidden.png"] {

background-position: -150px -50px;

}

img[src$="/images/skins/iconsets/default/icon_user.png"],

img[src$="/images/skins/iconsets/default/icon_collection.png"],

img[src$="/images/lockblue.png"] {

width: 0 !important;

height: 0 !important;

}

img[src$="/images/skins/iconsets/default/icon_user.png"] {

padding: 100px 0 0 100px;

background-position: 0px -75px;

}

.index:not(.comment) .abbreviated img[src$="/images/skins/iconsets/default/icon_user.png"] {

padding: 75px 0 0 75px;

background-position: 0px -375px;

}

.index:not(.comment) img[src$="/images/skins/iconsets/default/icon_user.png"] {

padding: 55px 0 0 55px;

background-position: 0px -525px;

}

#greeting img[src$="/images/skins/iconsets/default/icon_user.png"] {

padding: 1.786em 0 0 1.786em;

background-position: 0 -19px;

background-size: 201% !important;

}

img[src$="/images/skins/iconsets/default/icon_collection.png"] {

padding: 100px 0 0 100px;

background-position: -100px -175px;

}

.index img[src$="/images/skins/iconsets/default/icon_collection.png"] {

padding: 55px 0 0 55px;

background-position: -55px -525px;

}

img[src$="/images/lockblue.png"] {

padding: 15px 0 0 15px;

background-position: -155px -305px;

}

button,

.actions a,

.actions a:link,

.action,

legend .action:link,

input[type="submit"],

.actions a:visited,

.actions li label,

a.action.modal-closer {

color: #FCF5ED;

background: #A0153E;

border: 1px solid #A0153E;

box-shadow: none;

}

button:hover,

.actions a:hover,

.action:hover,

input[type="submit"]:hover {

color: #00224D;

background: #ff2071 !important;

border: 1px solid #ff2071;

box-shadow: none;

}

.actions li .current,

.current,

#dashboard .current {

color: #FCF5ED;

background: #ff2071;

border: 1px solid #ff2071;

box-shadow: none;

}

dl.meta {

border: 1px solid #a0153e;

}

.wrapper {

box-shadow: 1px 1px 5px #a0153e;

}

.actions input:focus {

border-top: 1px solid #a0153e;

border-left: 1px solid #a0153e;

box-shadow: none;

}

#dashboard .secondary {

background: #ff2071;

box-shadow: inset 2px 2px 5px #a0153e;

}

.alert .userstuff {

background: #ff91ba;

border-color: #ffd6e6;

color: #8a0035;

}

.qtip-content,

.notice:not(.required),

.comment_notice,

.kudos_notice,

ul.notes,

.caution,

.notice a {

color: #fcb6d1;

}

.notice,

.comment_notice,

.kudos_notice,

ul.notes,

.caution,

.error,

.comment_error,

.kudos_error,

.alert.flash {

background: #a0153e;

border: 1px solid #ff91ba;

}

.required,

.error,

.alert.flash {

color: #fcc2d8;

}

button:hover,

.actions a:hover,

.action:hover,

input[type="submit"]:hover {

color: #4f001b;

}

.comment img[src$="/images/skins/iconsets/default/icon_user.png"] {

padding: 55px 0 0 55px !important;

background-position: 0px -525px !important;

}

^ If you only read on desktop, this last bit is unnecessary. It fixes the blank profile pics from being too big on mobile, but in doing so, it does keep the pics small on desktop

EDIT: If you have any problems with the tags on mobile, go to media and select: "max screen and (max-width: 42 em)" and it should fix it!

[sagegarnish]

AO3 now has a tag for AI works!!! That means you can filter it out!* To filter it from your account, and never see any of it again, follow these steps.

- First, log in to your AO3 account

- Click on this link or paste this in your browser bar

https://archiveofourown.org/skins/new?skin_type=Skin

- Set "Type" to "Site Skin"

- Set "Title" to whatever you want (Something like “No AI” so you'll know what Skin you just made)

- Then click into the large "CSS" box and paste all of the bolded text below - hit the "Submit" button

.blurb:has(a[href*="/tags/Created%20Using%20Generative%20AI/works" i]), .blurb:has(a[href*="/tags/AI-Generated%20Text/works" i]), .blurb:has(a[href*="/tags/AI%20Generated%20Text/works" i]), .blurb:has(a[href*="/tags/AI%20Generated%20Fic/works" i]), .blurb:has(a[href*="/tags/AI-Generated%20Images/works" i]) { display: none !important; }

- Hit "Use"

Presto!

No more AI fics or art in your results! (assuming everyone tagged properly and your browser has the flags enabled)

A blocklist to be used with the Permablocking Specific Tags - Site Skin tutorial by Eli0t

*browser dependent

[fir-fireweed]

how did you learn to code IF? i really want to learn how to code twine games, i've used choicescript before but everything i have found about twine/sugarcube is so confusing and i don't know where to start. any tutorial recs or general advice would be so so amazing :)

Hi! I’m a big fan of Twine, which offers several story formats. I’ve found Sugarcube to be the most robust and extensive, but it’s also the most difficult to learn. I started on Twine Chapbook and I recommend it for beginners; it’s more limiting but easier to learn. Viatica is built in Chapbook if you’re curious how it looks.

Benefits to Chapbook:

It’s a complete, out-of-the-box format that requires no previous HTML or CSS knowledge. You don’t ever have to touch the style sheet like you do Sugarcube.

Chapbook is designed to be used on a variety of devices, especially mobile ones. It uses responsive design to adapt its page layout so that it's readable on any type of device without having to zoom in or scroll unnecessarily. Again, it’s already done for you.

There’s a single, easy to follow, comprehensive guide that tells you everything you need to know.

However, Chapbook doesn’t allow for a sidebar with characters stats, a codex, or multiple save slots. If you want those I’d recommend learning Sugarcube. There’s several guides and templates out there. The ones I found most helpful I have linked on my itch page.

I hope that helps! Good luck!

[shepherds-of-haven]

Wow the twine version looks gorgeous! I had no idea it was possible to do so much with twine, do you need to know a lot of code to be able to pull that off? May I also ask what map program you're using?

Hi there, thanks so much!! And to make a standard Twine game, you don't really need to know any code at all; the native, out-of-the-box version that you can download from twinery.org makes it very easy to make an interactive game, especially with the many free visual templates that creators put out there to help others get started!

However, to make a lot of what's in the ShoH Twine version now, that did unfortunately take a lot of code, none of which I knew at all at first! 😅 Figuring out CSS (to make the general UI, make it mobile-friendly, etc.), JavaScript (to create custom behaviors like the store, codex, and interactive maps), and twee (to code the game itself) ends up adding to a lot of work, let alone figuring out a good workflow system so that you can actually compile and test all of your progress. But resources like the Sugarcube wiki were invaluable when it came to getting started! Hope that all makes sense!

And I actually didn't use any map software for Shepherds: I drew the maps from my mind's eye on a tablet (which looked awful) and sent it to map artists I commissioned (who are listed in the credits) to bring my sketches to life! They did an amazing job (because my doodles looked horrible)!! However, if you're looking for good map-making software in general, I really enjoy Inkarnate, which I used more recently to map out the locations in my current novel!

[ryanyflags]

A List of Gender Terms !

So I disappeared for 2 months, but I finally completed this project! :D (Though I've been making some random posts talking about it, so it's not like I was really gone, or what I was working on wasn't obvious.)

It started off as me having trouble keeping track of a couple gender terms (and also not knowing they existed before, since I've never really seen people talk about them), then I thought I should make a list, and if I was going to do that I might as well post it to help other people too. Which I started out trying to make that list on Tumblr, but I found it too limiting so I moved to google docs, which I also found too limiting (I just couldn't achieve my vision, if you will), and now I know html and css.

As usual, I kinda overdid it, but I think I should be a little proud of myself. I had 0 knowledge of html and css, and 2 months later I've made my own website. (I could have made it much quicker, but I often had to take breaks, a bit overwhelmed by all that new stuff.)

Anyways, it has a ton of terms on there.

I have sections for nonbinary, abinary, midbinary, atrinary, midtrinary, androgyne, agender, neutrois, maverique, ilyagender, aporagender, outherine, kenochoric, and xenogender.

For 7 categories (sex terms, adult, general term, child, gender quality, gender-quality-in-nature genders, and spectrum / -iagender spectrum).

And they all have sources on both Archive Today, Wayback Machine, and if still existing, the original post too. (At least to the best of my abilities, and there are a couple of exceptions that I couldn't figure out.)

I did put effort into this, but it's possible I missed something. So if I made a mistake anywhere, or if anyone has any extra information to add on, or if you just have some comments, you can tell me. My ask box is open, but comments on this post would probably be fine too.

Also, I checked on a couple of different browsers, mobile too, and read up on web accessibility and checked and all that (I tried using a screen reader, I'm not a pro at it though, so it's possible I may have missed something obvious), so I hope the website itself is useable. But if there's any bugs there, just tell me (it'll be appreciated).

I'm also thinking of making another compilation, but for flags (for all of the terms listed here), and maybe orientations too, but maybe later haha

I also don't know how to write a image id for the top picture, if anyone wants to write to one I'll add it.

-

Below the cut is a short little video scrolling through the site.

[prokopetz]

Hi, Mr Prokopetz, I'm a big fan. Apologies if you've answered this before, but I was wondering what software you use to create the pdf and epub layouts of your ttrpgs, and whether you'd recommend it to a hobbyist who wants to try putting together something more professional than a gdoc for their own ttrpg?

My workflow is unfortunately not terribly accessible unless you have a fair amount of technical know-how.

In brief, I write all of my games in Notepad++ as HTML documents, taking care to use only the subset of HTML5 tags which are supported by most popular EPUB readers. I then use Calibre (or, more, precisely, the command-line utility that comes with Calibre, though you can get mostly the same results via the GUI) to bundle the HTML document as an EPUB3 file. I typically distribute both the HTML and EPUB versions (the former in a zipfile with all of the fonts and images and such) because web browsers tend to have much better screen-reader support than EPUB apps do.

The PDF, meanwhile, is generated from the same master HTML document using CSS paged media extensions – the layout is all generated automatically based on rules specified in a big, gnarly CSS file, and is never touched by human hands. There are a number of software packages which can do this sort of CSS-driven HTML-to-PDF conversion, some of them free or open source; I use a commercial product called Prince because, to the best of my knowledge, it's the only such software which has out-of-the-box support for PDF/UA semantic tagging (i.e., the stuff you need to do in order to make your PDFs screen-reader friendly), but you have more options if you're willing to tag your PDFs manually. (I am not.)

As for whether I'd recommend doing it this way? Like I said, unless you're a proper gearhead, not really; it's super efficient once you get it all set up – the only version of the game I actually maintain is the master HTML document, and generating updated versions of all the other formats is a one-click affair – but it's really only feasible for me because I already knew how to all that workflow automation stuff for unrelated reasons. I can't imagine teaching yourself all that from scratch just to write elfgames!

[5ummit]

Permanent Blacklists for AO3

Would you like to permanently remove fics with your squicks, triggers, and dislikes from all AO3 searches by default so that you never have to think about or encounter them again? Well now you can!

The ability to do this has actually been around for a little while but it relies on some new CSS functionality that wasn't supported on all major browsers until fairly recently (though you may still have to enable it manually on some). I'm not going to explain how this method works or how to code AO3 skins in general, as I've only dabbled in it a little and there are already some very good tutorials out there. If you want all of the details, check out these guides:

Skins and Archive Interface FAQ – The official skins guide created by AO3. Lots of good information but might be overwhelming and confusing for a beginner.

A Non-Extensive Guide on How to Start Creating a Skin for AO3 by ao3skin – Some good, fairly easy to understand, beginner info on CSS and specifically how it applies to AO3 skins.

Permablocking Specific Tags - Site Skin by Eli0t – Everything you need to know to create permablock lists. If your blacklist doesn't seem to be working as expected, check this for troubleshooting tips.

What I can offer though are some handy pre-made blacklists that you can use as-is or as a starting point to create your own so that you don't have to go to the trouble of figuring out how any of this works or hunting down relevant tags. Just copy the code, open AO3, go to My Preferences > Skins > Create Site Skin, paste it in the box, title it, and click Submit!

Note: The following lists are very specific to me and my own personal tastes. Absolutely no judgement if you love any of the things that I choose to blacklist. You do you. I just happen to like my fics fucked up and relatively canonical.

★ No Reader Fic – Hides all self-insert and reader fic.

★ No Alternate Universes – Hides anything tagged with the most common AU tags. There are so many incredibly specific AUs there's no way to list all of them and AU tagging is also extremely inconsistent from fic to fic so this blacklist may only catch 80% of AUs, but that's better than nothing. You could always exclude the entire alternate universe tag, rather than trying to list specific ones, but unfortunately canon divergence and other less extreme AUs would get caught in the crossfire, which is not worth it for me.

★ No Fluff – Hides anything tagged with the most common fluff and romance tags. I specifically left out "fluff and angst" though because sometimes that's used for things that are mostly angst with only a bit of fluff and I do love angst.

★ Bonus: No Dead Dove – This list is not mine (for obvious reasons) but I know some people may find it useful. Hides anything with the main archive warnings and many common problematic, taboo, or controversial tags. Some of these I wouldn't even classify as dead dove, they're literally just kinks, so I'd suggest reviewing the list carefully and removing any that don't apply to you.

Additional Notes:

This system doesn't work exactly the same as AO3's exclusion filters because you can't use top-level wrangled tags to block all subtags. It only blocks exact matches.

Once the blacklist is implemented you'll see no indication that anything was blocked (except for fewer fics listed on each search page); the entire blurb will be hidden. The tags and fic counts listed in the filter bar will remain unchanged. If you want more advanced features like whitelisting or adding something to indicate when a fic was removed, check out the permablocking guide by Eli0t.

Here's a link with info on which browsers currently support the new "has()" element, which this blacklist system relies on. As of right now Firefox for desktop still has to be manually enabled (for instructions see the section on flag enabling in the permablocking guide). Firefox for iOS isn't listed on this website but it seems to work fine for me.

There are other browser-specific extensions that let you permablock tags, such as this one and this one, that may be more a little more user friendly, but I've never tried them so I can't vouch for them and they may not work consistently between different devices. The good thing about doing blacklists via skins is that, after setting it up once, it should work automatically on pretty much any device (as long as you're logged in to your AO3 account).

[bloodsadx]

sorry if you’ve answered something similar before but how do you format things for your website? in the collections you have for poems

i love how it looks. the book kind of format it has

and i want to do similar/the same formatting for my own works but im really struggling…

i've been asked stuff like this a lot and i don't mind explaining it often because i want people to make websites more. i made a tutorial video at some point but it's kind of hard to make a curriculum or tutorial or whatever around this kind of thing because it's really just a self expression thing. i'll try to break down as much of my thought process as makes sense.

i design my pages in photoshop with either double/single page display in mind and then i use html to set them next to each other. most of the choice here comes down to how overwhelming i want my designs to feel. in the case of the lonely leaver page, the entire book was designed to be something that could be a physical book, and so from the getgo i made the pages in that kind of format. i previewed things in acrobat which has a booklet view mode (which singles out the front and back cover around the contents of the file) & allows you to process double page view as well. as for the actual process in photoshop before that point, i typically will open a canvas that is the size of the full 2 page spread (i.e. 8 inches wide for 2 pages which are both 4 inches wide) and i set grid lines for bleed margins and to mark the center of the page so that i can make the composition something that im comfortable with having a gap in the middle from the book folding. with lonely leaver i had to reformat about half the book at some point because i wanted to make it a larger resolution which was annoying but i just keep my guidelines for a print size in mind while im working. often if im a certain amount of time into a project that i feel like i will be spending a lot more time with i'll create a dummy psd file at this point which is devoid of content but which has all of the margins/resolution stuff set up already so i can just open that up and save a different version of it when i'm done.

my actual writing process and my design process is generally extremely intertwined, that's why things tend to be varying degrees stream of conscious in my work i think. i'll for instance, have a thought im stuck on for several days, and then open photoshop without having a poem or comic in mind, but i'll fill the canvas with some kind of color like red or yellow or a photo or whatever, and then open a text box or start drawing. telling a story through composition (i.e. page layout itself) is generally my favorite aspect of art and design because i enjoy how violent and dramatic framing angles can make the content of a piece feel so i'll try to move stuff around as much as possible in order to get my desired effect, often times using place holder shapes in lieu of finished design elements in order to get a rough blocking. as i do this i tend to react to what i'm writing/making as i'm doing it, and i do a lot of selective self editing during this part. for instance, i'll start manipulating rasterized text or cutting around images or whatever. i'll reread and look at whatever im doing for a couple of hours and then when i'm done with a spread or whatever i will save the document as a psd with a combined full spread and then each page separately as pngs or whatever (split at the middle grid line, back to the example, i'll save 2 different 4 inch wide images by changing the canvas size).

when it's time for me to put stuff on my website i then batch convert whatever pngs i exported into webp's because they load faster and take up less space on the server/my computer. you can look at my direct html/css files in your internet browser's explorer mode to see exactly what i do but essentially i just have either 1 or 2 images in a block and then a series of repeating vertical blocks containing images. i don't have an extremely efficient way of uploading pages and i'll typically just copy the same

"<p><img src="01.png"> <p><img src="02.png">"

like, 30 or 40 times or whatever into a html document. i use visual studio code for this stuff because it lets me do a bunch of stuff like having several files open at once & the navigation pane is nice & there's a live server extension that automatically refereshes the html file in my web browser on file save which is really awesome. i have a css page that i made like, 5 years ago, and i usually just link new projects to that because it has a bunch of different settings in it which i'll toggle on or off depending on the needs of whatever page or i'll add new div id's to it. it's kind of messy at this point, but it gets the job done. i use filezilla and something like bluehost or something for webhosting/file management.

i arrange and organize all of my art extremely methodically so usually in my like "<root catch all poetry folder>" inside of my "<root catch all art folder>" there will be a "<name of specific poem book>" folder which just contains the poems named by their actual name e.g. "dedication to saint eulalia 4.png" and then another folder inside of that is called "paginated" where i, using the acrobat document i arrange stuff in as reference, rename copies of my pages which i have placed in that folder to be named things like "01.png" so that i can then manually flip through it sequentially in the windows photo viewer and also just so that i don't have to go through the arduous process of renaming and tracking stuff inside of the root folder i'm containing that project's files in.

i'm 26 now and i made my first website when i was like 18, and my first zine project and i'm tired of feeling feeling around that same time, so i've got like, coming up on a decade of trial and error behind this and this is generally what has worked for me. my website isn't super complicated and mostly just gets the job done but because i try to think about style and presentation up front with whatever projects i'm doing i tend to just make plans based around that as early as it makes sense. to me having a website for art presentation has always been the Primary Method and intended landing zone for my art so it's genuinely always been a consideration in my process to try to plan around how i will put it on my website. i do this because i believe having my own curated space for containing my art allows it to exist in a context which best heightens whatever message i'm trying to convey. if there's an issues with my website right now they are that i'm very bad at mobile browser formatting & i havent updated the main look of the website in something like 4 years barely at all.

anyway, at the end of the day i think really as long as you can identify whatever your intentions are and do some planning/problem solving around that you should probably be able to find your own method which works for you better than mine might but if you do just want to copy my website the tools to do so are within your brain and internet searches and i believe in you. i think the biggest strength of my website is that it shows how easy it is to just put art big as fuck on a webpage and how effective that kind of minimalism can be. i just want my website to be like a museum's walls. and it's not super complicated to get to that level of html knowledge.

[pawborough]

Beta Update

Alright everyone! We've gotten started on fixing the Guild (though no official push yet), and we were able to get started on our bug report and task sheet we're going to publish. We made halfway progress on the support articles we'll be publishing, and we got through a good chunk of bugs today, including:

* An infrastructure error which was overloading the server with so many accounts, fixed many latent issues on the backend. Many of the errors you see are remnants of it, but things should be smoother from here

* Midwife freezing

* User profile CSS box display

* Users online counter (something quick we got working during downtime!)

* Got many users through onboarding and tackled a bricking issue

* Mobile formatting issues: currency, nav dropdown, and onboardingWe've requested server expansion from our provider, which should also help. And we've replaced a good bit of flavor text! We will continue the replacements in between the big tasks!

Hopefully we'll be able to complete those articles by tomorrow! Here is what else we'll continue working on when we're all back on the grind:

* Latent breeding issues

* Guild problems

* Metamorphic item issues (incense, breed changes, etc.)

* General item functionality issuesItem functionality is our next big step following the Guild!

As always, I'll return in the morning to attend to any issues cropping up and update in real time as we work! Though it's the weekend, so we may see slower updates on the development end as some of our team is off. I'll be here though! I'm fading a little right now, so it's time for some rest!

Have a good night and a good weekend, catfolk!

[hotd-bigbang]

How to Submit Your Story to the AO3 Collection

Please read this guide carefully before submitting your story - we recommend having this page open at the same time, to follow along with, if you have never submitted a story to an AO3 collection before. Ensure that your accompanying artwork is finished and ready to go before submitting, and ensure all works are added to the collection before 23.59pm September 15th.

Please do not submit your story until it is ready - ensure all changes are made in your Word or Google doc. Updates to your fic once placed in the collection result in multiple draft copies, which we have to reject, so please don't submit until you are ready to hit 'post' (please hit 'post' and do not save as a draft - hitting post will successfully submit your fic to the collection and hide it until its reveal date)

Artists, you do not need to do anything. Send your artwork directly to your writer and they will handle the upload.

Step by step instructions below the cut.

To ensure that the artwork in your fic adapts to the right shape and size, depending on whether users are reading on mobile or desktop, you will need to create a workskin - do this first.

Log into your AO3 account and go from Dashboard to Skins

Go to My Workskins and Create Workskin

Choose "Work Skin" if it's not the default

Title whatever you like; description is optional

Type in the CSS code shown below exactly the way it is here:

#workskin img { width: auto; max-width: 100%; height: auto; }

(We recommend copying and pasting, so there are no mistakes)

On the bottom right under "Actions" will be the option to Submit for you, tap/click and you're done!

Once you're done, you choose New Post in the top right of your browser. You fill out the Rating, checkmark the right Archive Warnings, choose the Fandom (i.e. House of the Dragon in this case), the Category that applies to your story, the Relationships and Characters. Last but not least, you put in the Additional Tags (i.e. more warnings, or triggers).

You get to the point where you put in the Title of your story and Co-Creators, this is where you'll list the Big Bang account, more details on this further down. Then follows the box to fill in your Summary. If you want to add a note at the beginning or end of a chapter, you checkmark the option and a box will open. Whatever you write in there, please note it will be gone if you uncheck the box.

Type in "House_of_the_Dragon_Big_Bang_2024" under Post to Collections/Challenges and select the Collection shown in the description.

Under Gift this Work to, you should add your Artist and Beta Reader. As a co-creator, please add hotdbigbang.

Select the This Work has Multiple Chapters if your story has more than one chapter.

And last but not least, you Select your Work Skin before you get to the part where you can paste in your story.

Finally, posting the art to your story within the story:

Choose Rich Text

Tap the image icon

Once you have tapped the image icon, a little box window will open in which you have to insert the Source. Writers, you get the image address to insert from your Artist.

Not all image addresses work, the most effective are from Discord or Tumblr.

Please add an Image Description of the image you are posting, it will be for those who use TTS- text to speech to have someone read the story, that includes visually impaired people, but also those who simply like it to listen to a story. It will be nice for them to hear what they would see in the image. You can be as detailed as you like.

Next is Width and Height, both get automatically generated and even if the image pops up really big when you tap Save, remember you used a Work Skin that will adjust it accordingly for your readers once posted.

Hit submit and you are done! Your fic will remain unrevealed in the collection until your reveal date. We will post the full reveal schedule closer to the deadline.

[stickia404]

You know what? I need to make a new intro post.

Ello! I am Stickia/Sophia (She/Her) (Stick, Stickia, Arco, Sophia, etc) and I am cool with any of the names, but I do like Stickia/Sophia more. I have quite a few interests, some of them being, but not limited to: Minecraft, Modded Minecraft, Coding, Hex Casting (the MC mod), Blender, General 3D art, and more.

I typically just reblog posts rather than make them, so don't follow me if you don't want your blog to have lots of reblogs lol. Also, my ask box is always open, and empty, so don't be scared to ask me something there or tell me when I have done something wrong.

As for tags I use, I mostly just use them as side thoughts for posts, but I do tag long posts as "long post" or "do you like the color of". Other than that, I only really tag TWs. Also, I don't really have a DNI, except for don't be a dick.

Now I have an Art Blog! You can find it over at @artwood-post. I likely reblog all the posts there too here, but still give me (it?) a follow.

If you want to hear more about my self, you can visit my own basic HTML/CSS website. Found here: https://stick404.mindlesstoys.com/info.php There is still a lot to be worked on about it, but I am (slowly) improving it (also yes, I know about the spelling errors lol, just have not uploaded the changes yet).

New Icon was made by Abyst, go check them out!

As for coding: I am working on probably my largest project ever! Magma, a Lisp Interpreter in Java. It was originally inspired by Minecraft Mods like Computer Craft, and is based on the core of TinyLisp, however I am planning to expand it much more. Right now, I have made a registry for both Functions and Expressions, and reworking the core Eval-Loop to use Stack Safe recursion. Feel free to read over and maybe even make PRs! (but its right now in a state of rapid change, so it may not work)

[irlmaeda]

Hiya! I found your blog through your neocities website! I was wondering if there’s any tips or things you read/watched that help you make your site. (Im heavily considering making one of my own neocities site it just seems fun)

hihi welcome !! i have quite a few pieces of advice, but the tldr is you should come up with an idea for what you want to make beforehand, and look up how to do each piece! your knowledge will start to fill in along the way :]

(this is probably gonna be long as hell so under the cut is all of the fun stuff /silly)

the way i personally started off was by sketching out what i wanted my site to look like! if you know what you want before you begin, you'll know where to look to figure out what you need to do. html+ css are extremely easy languages to read/write once you know what to look for!

^ this was the original sketch for my site, where i planned out everything i wanted to include. it's a bit different from what actually ended up on the site, but that's alright! it's just about having an outline to work from. i think of it like outlining before you write, it feels like such a pain in the ass because u just wanna start working NOW but u will thank yourself later for taking the time to plan.

once you know what you want to make, start looking for tutorials and resources to make it easier! the grid for my homepage and some of my other subpages was made using a css grid generator, since its one of the more confusing bits of css. you can make grids without it, but its a very easy way to make a more asymmetrical design if ur using the generator!

thats linked here, it gives you some css to put in your head or css sheet, and then the html for the different boxes to slap in your main document. it can be easier to understand what itll look like if you give each one a border while you work, even if its just temporary!

when looking for information about css and html, w3schools is your best friend. its a pretty comprehensive database of every little piece of html + css you could ever need, with examples you can play with yourself to understand what each variable does! it's been a lifesaver for me, ive watched basically zero video tutorials because everything on there is explained so well and you can find basically Anything.

they even have code snippets for things that take more than one or two lines of code, which you can use and adapt yourself! (the tooltips on the official art + my art sections on the hinata shrine were adapted from a tutorial on there!)

in general, having a plan and working from there will make ur life so much easier. the pages that ive sketched out beforehand or ive had a very clear vision for have been WAYY easier to code than the ones i tried to come up with on the fly, and ive been much happier with how they've turned out as well. though i do also have some smaller, rapidfire tips as well that ill go thru now!!

— inline css (the style="" tag) seems so so useful but really should only be used when you're resizing images like buttons. when u keep all of your css in the head or in a seperate document, its way easier to debug and read later. i cleaned up my homepage recently by removing all of the inline css and looking at the code stresses me out WAY less because i can actually read it LOLOL ... plus cutting the css out and putting it in its own document made me realize that id accidentally wrote some really weird code in some places

— this is very much 'do as i say, not as i do,' but use an external editor (like visual studio code) instead of editing live on neocities! you can set up a live preview, and generally wont be pushing out 100 updates every single time you change or add something. i tend to code directly on neocities but its a bad habit and i want to break it eventually v_v

— if you really like an effect someone else has on their site, you can peek using inspect element i promise the coding police won't get you !! dont steal code line for line, but you can figure out what theyre doing and put your own spin on it. things like border images can be really cool, and i only figured out about them because i looked at what someone else was doing and figured out how to adapt it for my own site! check linkbooks and credit sections as well, a lot of people will include links to any effect they didnt make themself or got help with. (including me! the credits section of the linkbook has a ton of little things i got from other places, including a really neat little music player, the rss feed for my status cafe, and the wobbly text on the homepage!)

— most stuff in html and css basically just... says what it does in the tag. so looking stuff up for it is extremely easy! if you've used carrd before you honestly probably already know more abt html than u'd think just intuitively. when ur adjusting the margins or padding in carrd, you're adjusting the margin: and padding: properties in the css of the website it's outputting!

this is getting way too long but!! my best advice is to just get started. you'll never be able to learn without trying, and it genuinely is so fun to have something that's truly your own!

(if u have any specific questions im happy to answer anytime as well! i love talking abt neocities, its a super fun hobby and way easier to pick up than u would think!)

[fearoffun]

hi there!! there isn’t a need to publish this ask I literally just am so curious if you had any resource or tutorial regarding your neocities! I’m sorry if this is so out of the blue but I saw your site and really adored the layout!! I’m specifically just wondering about the method you used for your blog posts - I’ve found some recommended ways to do it but i feel like yours is integrated really well imo :) also if you’re not comfortable answering or anything that’s totally fine lol pls don’t feel obligated. lastly your art is so gorg!!!

i'm finally going to answer this ask...!! it's going to be a very long read so i'll keep it all under this cut

i know you are specifically curious about the blog posts page but i figured this was a great time to thoroughly explain my website layout too since i had another person asking about it (i'll put that at the bottom though) :D

please bear with me btw because i... i have never made a tutorial like this before LOL

--

blog posts guide

1. scrollbox

i made a super low effort format for my blog entries. i honestly just wanted it to be a super simple scrollable box with all of my entries being in one general place. CSS to do this, i created an all encompassing <div class> that had the styling property of overflow.

fyi, i also added a <div class> within the scrollbox class that would handle the padding but TBH i'm not sure... i needed to make an entire class for that LOL REFERENCES - scroll box

2. date & time

HTML ok honestly i just used a <p> element and made it bold....

3. images (optional)

HTML i don't always attach an image to my entries but when i want to, i use this <div class> that sits below my date & time. i style it with an <img class> that i created and add an <alt text> too to make it more accessible!

CSS this is what the <img class> looks like. i like my images centered and on their own "line."

4. status

HTML again, another <div class> specifically made for the status. i just made the font size smaller to visually differentiate it from the actual entry itself.

5. blog entry text

HTML my blog entries are simply typed up between <p> tags and i use <br> to start a new line... it literally just looks like this LOL....

THAT'S ALL...>!!!!!! :)

--

website guide

1. general page layout

HTML in order to establish where i want all of my blog's content to lie, i created a <div class> specifically to store it all.

CSS the styling for it is pretty simple! just setting a max-width to limit the size of everything that will be in it and also centering the page with the margin.

2. sidebar

HTML my sidebar just comprises of a heading tag and navigation links.

CSS this is all personal taste aside from the fixed position

REFERENCES - fixed sidebar - responsive sidebar

3. main content

HTML because everything is stored in the <div class="content">, the sidebar and the page contents are limited to the constraints of the it.

that is all pt. 2...... bless <3